Description

Explores the idea explained here: #3248 (comment)

My intuition says this should be enough, under the assumption that eth_getLogs works properly with multiple addresses.

This solution has one downside: we can't define block number from which we want to start indexing new contract. The reason is how the indexing is continued after the autopilot restart: we check the latest indexed block in the database, and use that to continue indexing. And this solution assumes that old and new contract indexing is completely synchronised and atomically inserted into database. So, bottom line, new contract events would be inserted from the point when new contract address is added to the autopilot configuration.

IMO, this tradeoff is fine considering other solutions complexity.

To verify, e2e test will be written.

TODOS:

1. Refunder service needs to be adjusted to work with multiple contracts
2. Write e2e test

Changes

• ...
• ...

How to test